[. . . ] Red Hat Network Satellite 5. 3. 0 Channel Management Guide Red Hat Network Satellite Channel Management Guide Red Hat Network Satellite 5. 3. 0 Channel Management Guide Red Hat Network Satellite Edition 5. 3. 0 Copyright © 2009 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1. 0 or later (the latest version of the OPL is presently available at http://www. opencontent. org/openpub/). Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. All other trademarks referenced herein are the property of their respective owners. [. . . ] Review the impending changes on the confirmation page and click Update Errata. · Packages -- Provides the packages associated with each of your custom channels. This tab contains subtabs that allow you to view, add, and remove packages: List/Remove, Add, and Compare. · List/Remove -- Displays all of the packages currently associated with the custom channel and provides a means to cancel that association. To remove packages from the channel, select their checkboxes and click Remove Packages on the bottom right-hand corner of the page. Click Confirm to complete the action. Important This list differs from the package list available through the standard Software Channel Details page in that it displays all versions of a package remaining in the database, rather than just the latest. You may revert to a previous version of a package simply by removing the latest version. To see available packages, select an option from the View dropdown menu and click View. To add packages to the channel you are editing, select the appropriate checkboxes and click Add Packages. Refer to Section 4. 6, "Assigning Packages to Software Channels" for a discussion of this process. 13 Chapter 4. Custom Channel and Package Management · Compare -- Enables the comparison of package lists between different channels. To see the differences, select another channel from the Compare to: dropdown menu and click Compare. A list appears showing all packages not contained by both channels and indicating the existing channel location of each. 4. 4. Manage Software Packages In addition to adding and removing packages within channels, you also have the option of deleting packages entirely from both the database and file system. This can be done through the Software Package Management page, accessed by clicking Manage Software Packages on the left navigation bar. Warning Although deleting packages from the database can be undone by uploading them again, they lose their association with any errata. To remove packages from the database, in the Software Package Management page, select an option containing them from the View dropdown menu and click View. Since the actual packages are stored on the RHN Proxy Server, its custom packages cannot be downloaded through the RHN website, although they are listed. Since the RHN Satellite Server provides its own website, its custom packages are accessible via HTTP or Red Hat Update Agent. To obtain custom packages, the client system must be subscribed to the channel containing the packages. 4. 5. Creating a Software Channel Before uploading packages to the server, a custom channel can be created to house them. Refer to Chapter 6, Uploading and Maintaining Custom Packages for instructions. Once uploaded, packages may be reassigned through the website, as described in Section 4. 6, "Assigning Packages to Software Channels". [. . . ] Without this option, uploading a pre-existing package returns an error. Forces RHN Push to drop the username and password cache, then accept or ask for new ones. This is useful if you make a mistake entering them the first time. -n, --count N_HEADERS_PER_CALL -l, --list -r, -reldirRELATIVE_DIRECTORY -o, --orgidORGANIZATION_ID -u , --username USERNAME -p , --password PASSWORD -s, --stdin -X, --exclude GLOB --force --nosig --new-cache 25 Chapter 6. Uploading and Maintaining Custom Packages Option --newest Description Push only the packages that are newer than those on the server. [. . . ]